Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Supports oneof fields in more places #416

Closed
wants to merge 4 commits into from
Closed

Conversation

yugui
Copy link
Member

@yugui yugui commented Jun 17, 2017

The idea behind the change is similar to
golang/protobuf#283.
But it returns a non-nil pointer to an oneof option struct for
ease of use in both of unmarshaling and assignment.
@yugui yugui requested a review from tmc June 17, 2017 03:45
@yugui
Copy link
Member Author

yugui commented Jun 18, 2017

I noticed that the alloc function does not work when the target message is defined outside of the current package. I'll rewrite this PR.

@mcos
Copy link

mcos commented Sep 13, 2017

@yugui What's the current state of this?

@abronan
Copy link

abronan commented Mar 7, 2018

Although it's relatively easy to find a workaround when in need of such a message structure, supporting oneof at the root of the request body would be awesome 🤗

Is there any help needed to push this PR forward?

@achew22
Copy link
Collaborator

achew22 commented Mar 8, 2018

@abronan, if you want to fork @yugui's branch and take a stab at it I would be happy to help you get it past the finish line. I agree that oneof at the root would be a nice feature. It just takes a little bit of finesse

@yugui yugui mentioned this pull request Apr 30, 2018
1 task
@tmc
Copy link
Collaborator

tmc commented Jun 19, 2018

This is replaced by #634

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

oneof fields are not supported as the "body"?
5 participants